
=============================================================================
HL-Server TSR - History of changes
=============================================================================

2.76  Jul 1998

* Please note that, in contrast to HLS32, HLS32SVC and NLM, the TSR
* supports only three Hardlocks, and it does not support automatic
* adding of requested Hardlocks. Due to memory restrictions in a
* DOS environment, this will NOT be changed in the future.

- API_READ_ID function supported

2.74  Feb 1998

- Duplicated counters problem fixed
  If an HL-Server was accessible via IPX and NetBios on different MAC
  addresses, both USERINF and MAXUSERS could be duplicated in former
  versions. You must use new (Feb. 1998) HL-Servers and APIs for this
  fix to work (of course, you can mix old APIs with new Servers and 
  vice versa if you are not concerned about this problem).

- veni-vidi-vici switch renamed to -v (verbose)

- startup banner of menu surface removed
_____________________________________________________________________________

2.72

- MS TCP/IP 32
  Switch Xnnn (nnn=bit coded value)
  bit 0=1: WfW 3.11 NetBios over MSTCP32 compatible mode
  (see HLS_TCP.* file)
_____________________________________________________________________________

2.71

- MS TCP/IP 32
  Using NetBios over TCP/IP, the address field is used in a
  non-standard way. HLS now circumvents this problem.
_____________________________________________________________________________

2.62

- SAP reply uses SAP source socket
  this is no change in function, but maybe needed by some bridges/routers
  an eases troubleshooting

- HL-Servers prior to version 2.50 are found again by the menu surface.

| MainStat and SubStat return "Level" in Shortlife
_____________________________________________________________________________

2.61

| Signature "LOGINS" not longer needed in Glenco Version
_____________________________________________________________________________

2.60

- Surface
  New SAP-Search: no longer Bindery used, now via SAP Query
  This works without NetWare-Shell, also under NT, Win95, ...
  Finds NLM since V1.0 and TSR since V2.55

- Check if HLS already running on same node address.
  Refuses loading if running in another DOS box.
  NOTE: Since Bridges and Routers store SAP server addresses and need some
        time since releasing the entry after HL-server terminates, you
        may have to wait up to a some minutes after unloading HL-Server
        before you can reload it again. The exact time depends on the
        size (i.e., number of bridges/routers) in your network.

_____________________________________________________________________________

2.55

- SAP-Responder in HL-Server
  TSR answers directly to SAP "Get nearest Server" requests.
  With this feature _new_ Client-API's (starting from version @@@@) are able
  to find HL-Server on other segments even without a NetWare Fileserver.

_____________________________________________________________________________

2.54

- The "LOGINS" signature in the application hardlock is considered valid
  even if no valid number follows. In this case, the number of logins
  will not be restricted, it will be equal to your HL-Server licence.

_____________________________________________________________________________

2.52

- HL-Server now supports a 5-User-Licence

_____________________________________________________________________________

2.52

- Bugfix:
  An internal HL-Server status query (exclusively used by the HL-Server
  menu surface) replied twice. In rare cases, this produced a display
  of phantom module addresses during a rescan in the HL-Server menu
  surface. This symptom occurred in OS/2 Dos boxes only.

- HL-Server menu surface:
  The Hardlock's RAM contents and the example encryption string can not
  longer be edited.

_____________________________________________________________________________

2.51

- Low level function API_DOWN implies API_LOGOUT

_____________________________________________________________________________

2.50

- HL-Server accepts client requests from arbitrary socket numbers
  and uses the clients source socket for its reply.
  Clients running in a (pseudeo-) multi tasking environment may now
  user a private socket number to avoid conflicts, if multiple clients
  are running on the same node address.

_____________________________________________________________________________

2.40

- HL-Server now supports the new HL-Server external Hardlock

- Please remember: HL-Server Hardlocks still require to contain the
  "LOGINS:nnnn" signature in the ROM.

- New combination possibilities for HL-Server Hardlocks:

  Up to three Hardlocks with the same module address can be attached to
  one HL-Server. Their licences, inculding limitations by a
  "LOGINS:nnnn" signature, are automatically added. Thus, you can
  upgrade licences by simple sending an add-on Hardlock to your
  customer. (The maximum number of logins for one module address cannot
  exceed 250).

  Example:    HL #1:  Module Addr. 12345
                      Licence         10
                      Signature    LOGINS:0007

              HL #2:  Module Addr. 12345
                      Licence         20
                      Signature    LOGINS:0015

  Using this two Hardlocks with an HL-Server (started with HLSERVER
  -m:12345) results in 22 login entries for this Hardlock.

  CAUTION: Hardlocks with identical module addresses must be located at
           different port addresses. If two Hardlocks with the same
           module address are plugged at the same port, only the first
           of them will be used.

  You may use this licence addition feature for up to three different
  module addresses at one HL-Server.

  Example:

        LPT1             LPT2           HL-Server Card

        #12345           #12345         #34567
        20 users         100 users      20 users
        LOGINS:0015      LOGINS:0080    LOGINS:0020

        #23456           #34567
        10 users         100 Users
        LOGINS:0010      LOGINS:0085

    Using the command line "HLSERVER -m:12345 -m:23456 -m:34567", you
    will get the following login tables:
        Hardlock 12345:   95 users
        Hardlock 23456:   10 users
        Hardlock 34567:  105 users

_____________________________________________________________________________

2.32

- External application Hardlocks *must* contain a signature
  "LOGINS:nnnn" in the ROM area of its memory. "nnnn" is the maximum
  login count as a four digit decimal number (e.g., "LOGINS:0010").
  This was invented to avoid the misuse of local hardlocks with the
  HL-Server. The demo mode with Hardlock MA=29809 doesn't need this.

- Server Hardlock background check
  The HL-Server Hardlock is checked continuously in the background. If
  it is removed while HL-Server is running, the HL-Server software
  ignores any requests and plays a tune until then Hardlock is
  replugged.

- The startup memory test was changed, so the HL-Server startup time may
  be a little bit shorter.

- Any Netware File Server's Internal Bridge does not longer echo the HL-
  Server reply packets on a single segment network. This was not a
  problem, it was simply unnecessary.

- The packet info field "Packet type" was changed from "unknown" to
  "IPX". This has no effects to function, but it looks better when
  monitoring packets with LanSight etc.

- Quick Hardlock memory access may be disabled
  The contents of the Hardlocks served by HL-Server is cached for
  maximum performance. When the memory contents is changed locally
  at the HL-Server machine, these change are not recognized when the
  Hardlock is accessed remotely. The new -Q option avoids these problems
  by disabling the cache. The default value is caching active.

_____________________________________________________________________________

2.30

- Application Hardlocks must contain the signature "LOGINS" in their
  memory's ROM area.
  The Signature is not case sensitive and is recognized in lo/hi
  and in hi/lo byte order.
  HL-Server demo mode with demo Hardlock 29809 works without
  this signature.

- Server Hardlock background check
  If the server Hardlock is removed while the HL-Server is running,
  HL-Server does not reply to client requests; it appeares to be
  not loaded.
  The machine running HL-Server also produces a warning sound.

- Faster memory existence test implemented

- The Netware fileserver internal bridge does not longer produce echo
  packets if there is only one network segment.

- The info field "Packet type" in the IPX header was changed from
  "unknown" to "IPX". This is no functional change, but produces a
  better look when monitoring packets.

_____________________________________________________________________________

2.21

- Surfaces uses Critical Frame with CLI/STI
- Improved INT2F Signature
- HLSERVER.HLP included in HLSERVER.OVL
- adjustable mailbox size -Bnn 6..128
- for using Demo mode, the 29809 Hardlock doesn't need memory
- Midnight time correction my be enabled by -MTC or -MIDNIGHT switch

- TSR size reduced by approx. 12KB by splitting HL-Server into
  modules internally.

_____________________________________________________________________________

2.20

Bugfixes
--------
  - Time Correction caused date problems
    - Time Correction eliminated
  - Mouse usage in WIN31 windowed DOS box caused problems
    - fixed, WIN31 is detected automatically
    - to provide a workaround in case of other mouse related problems,
      a new environment setting is available: SET HLSERVER=TEXTMOUSE
      forces usage of the standard textmode mouse cursor instead of the
      graphical cursor
  - IDLE function works with module address wildcard

New Features
------------
  - SAP used on Novell systems
    - HL-Server on IPX works across bridges
    - Remote/Select and Remote/Rescan are much faster
    - remember that ELS and LITE *do not* support SAP
_____________________________________________________________________________

2.11

 - Bugfix: RAM was not included in the "Logins:nnnn" search
           - new search order:  ROM LO-HI
                                ROM HI-LO
                                RAM LO-HI
                                RAM HI-LO

 - New   : The "Logins:nnnn" signature also takes effect in demo mode,
           i.e. in the RAM area of a 29809 Hardlock
_____________________________________________________________________________


